docs(pools): clarify profile updates don't propagate to idle pool browsers#354
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
|
Firetiger deploy monitoring skipped This PR didn't match the auto-monitor filter configured on your GitHub connection:
Reason: PR only modifies documentation (pools FAQ) with no changes to API endpoints or Temporal workflows. To monitor this PR anyway, reply with |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Risk assessment: Very Low.
This PR adds a single FAQ entry in browsers/pools/faq.mdx with no codepath, config, navigation, infrastructure, schema, auth, or security-boundary changes. The blast radius is limited to documentation copy for one browser pools page. I found no existing approvals and no CODEOWNERS file or requested codeowner reviewers, so I'm approving.
Sent by Cursor Automation: Assign PR reviewers
There was a problem hiding this comment.
Risk assessment: Very Low
This PR only adds a short FAQ entry to browsers/pools/faq.mdx clarifying browser pool/profile behavior. The diff is documentation-only, limited to one page, with no changes to codepaths, generated API references, navigation/configuration, infrastructure, prompts, or shared systems. I also didn’t find a CODEOWNERS file requiring owner review, and there were no existing approvals to preserve.
Approved based on the current diff.
Sent by Cursor Automation: Assign PR reviewers
1 participant
Summary
Adds a pools FAQ entry explaining that updating a profile's contents does not propagate to already-warmed idle browsers in a pool. Pool browsers load profile contents at fill time; the only way to force a pool to pick up new profile contents is to flush idle browsers (or
browserPools.updatewithdiscard_all_idle: true).Test plan
browsers/pools/faq.mdxNote
Low Risk
Low risk: documentation-only change that clarifies expected pool behavior and how to force refreshed profile contents.
Overview
Adds a new FAQ entry to
browsers/pools/faq.mdxclarifying that updating a profile’s contents does not propagate to already-warmed idle pool browsers.Documents the recommended ways to pick up updated profile data:
kernel.browserPools.flush()(to rebuild idle browsers via refill) orkernel.browserPools.update()withdiscard_all_idle: true.Reviewed by Cursor Bugbot for commit a9e88c5. Bugbot is set up for automated code reviews on this repo. Configure here.